@benoit74 , I am going to need your input on the permissions required for the offliner creation via API. I avoided using schedules, create=True because there are other roles with that permission that could not be prvileged to create an offliner. Left a todo comment on it. i don't know if this should be paused till #1419 is reviewed and possibly new permissions set.

WDYT?

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.84%. Comparing base (7e4bd19) to head (720ae29).
⚠️ Report is 6 commits behind head on main.

@@            Coverage Diff             @@
##             main    #1422      +/-   ##
==========================================
+ Coverage   82.74%   82.84%   +0.09%     
==========================================
  Files          79       79              
  Lines        3959     3952       -7     
  Branches      432      432              
==========================================
- Hits         3276     3274       -2     
+ Misses        564      559       -5     
  Partials      119      119              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

WP1 does not really have a UI to "select the version" they want to run and I figured they would also want to do similar thing. Because the API returns the versions as a list of strings in descending order of created_at. So, if they are going to select the version they would use by "choosing the first" because it should be the most recent, I figured it would be simpler to do it here and avoid one more API call. Same thing applies to Zimit frontend

Do you have an idea on how the selection should be done?

You probably saw that after your comment, just for the reference: openzim/wp1#1024 (comment) (we will configure the version in WP1 config file)